Finding ID | Version | Rule ID | IA Controls | Severity |
---|---|---|---|---|
V-68153 | SRG-APP-000319-MFP-000047 | SV-82643r1_rule | Medium |
Description |
---|
Once an attacker establishes initial access to a system, the attacker often attempts to create a persistent method of re-establishing access. One way to accomplish this is for the attacker to simply enable a new or disabled account. Notification of account enabling is one method for mitigating this risk. A comprehensive account management process will ensure an audit trail which documents the creation of application user accounts and notifies SAs and ISSOs. Such a process greatly reduces the risk that accounts will be surreptitiously created and provides logging that can be used for forensic purposes. To address access requirements, many application developers choose to integrate their applications with enterprise-level authentication/access/auditing mechanisms that meet or exceed access control policy requirements. Such integration allows the application developer to off-load those access control functions and focus on core application features and functionality. |
STIG | Date |
---|---|
Mainframe Product Security Requirements Guide | 2019-10-08 |
Check Text ( C-68713r1_chk ) |
---|
If the Mainframe Product employs an external security manager for all account management functions, this is not applicable. Examine account management settings. If the Mainframe Product does not automatically audit account creation, this is a finding. |
Fix Text (F-74269r1_fix) |
---|
Configure the Mainframe Product account management settings to automatically audit account enabling actions. |